Dynamic bandwidth allocation for wireless mesh networks

ABSTRACT

Apparatuses, methods, and systems for dynamic bandwidth allocation are disclosed. One method includes identifying, by a first distribution node of a wireless mesh network, a communication link with a second distribution node of the wireless mesh network, generating, by the first distribution node, a proposed bandwidth allocation schedule for wireless communication of information between the first distribution node and the second distribution node based on data traffic requirements of the first distribution node, wherein the second distribution node receives the proposed bandwidth allocation schedule, and wherein the second distribution node adjusts the proposed bandwidth allocation schedule based upon data traffic requirements of the second distribution node. The method further includes receiving, by the first distribution node, the adjusted proposed bandwidth allocation schedule from the second distribution node, and communicating, by the first distribution node, information with the second distribution node according to the adjusted proposed bandwidth allocation schedule.

RELATED APPLICATIONS

This patent application claims priority to U.S. Provisional PatentApplication Ser. No. 62/619,744 filed Jan. 20, 2018, which is hereinincorporated by reference.

FIELD OF THE DESCRIBED EMBODIMENTS

The described embodiments relate generally to wireless communications.More particularly, the described embodiments relate to systems, methodsand apparatuses for dynamic bandwidth allocation for wireless meshnetworks.

BACKGROUND

Multi-hop wireless networks include multiple nodes wherein wirelesslinks are formed between the nodes. Efficient usage of the bandwidth ofwireless links between the nodes is needed for high performance ofmulti-hop wireless networks.

It is desirable to have methods apparatuses, and systems for dynamicbandwidth allocation for wireless mesh networks.

SUMMARY

An embodiment includes a method of dynamic bandwidth allocation. Themethod includes identifying, by a first distribution node of a wirelessmesh network, a communication link with a second distribution node ofthe wireless mesh network, generating, by the first distribution node, aproposed bandwidth allocation schedule for wireless communication ofinformation between the first distribution node and the seconddistribution node based on data traffic requirements of the firstdistribution node, wherein the second distribution node receives theproposed bandwidth allocation schedule, and wherein the seconddistribution node adjusts the proposed bandwidth allocation schedulebased upon data traffic requirements of the second distribution node.The method further includes receiving, by the first distribution node,the adjusted proposed bandwidth allocation schedule from the seconddistribution node, and communicating, by the first distribution node,information with the second distribution node according to the adjustedproposed bandwidth allocation schedule.

Another embodiment includes a wireless network. The wireless networkincludes a first distribution node and a second distribution node. Thefirst distribution node operates to identify a communication link withthe second distribution node, and generate a proposed bandwidthallocation schedule for wireless communication of information betweenthe first distribution node and the second distribution node based ondata traffic requirements of the first distribution node. The seconddistribution node operates to receive the proposed bandwidth allocationschedule, and adjust the proposed bandwidth allocation schedule basedupon data traffic requirements of the second distribution node. Thefirst distribution node further operates to receive the adjustedproposed bandwidth allocation schedule from the second distributionnode, and communicate information with the second distribution nodeaccording to the adjusted proposed bandwidth allocation schedule.

Another embodiment includes a first distribution node. The firstdistribution node operates to identify a communication link with asecond distribution node of a wireless mesh network, and generate aproposed bandwidth allocation schedule for wireless communication ofinformation between the first distribution node and the seconddistribution node based on data traffic requirements of the firstdistribution node, wherein the second distribution node receives theproposed bandwidth allocation schedule, and wherein the seconddistribution node adjusts the proposed bandwidth allocation schedulebased upon data traffic requirements of the second distribution node.The first distribution node further operates to receive the adjustedproposed bandwidth allocation schedule from the second distributionnode, and communicate information with the second distribution nodeaccording to the adjusted proposed bandwidth allocation schedule.

Other aspects and advantages of the described embodiments will becomeapparent from the following detailed description, taken in conjunctionwith the accompanying drawings, illustrating by way of example theprinciples of the described embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows nodes of a wireless mesh network, according to anembodiment.

FIG. 2 shows distribution nodes and client nodes of a wireless meshnetwork, according to an embodiment.

FIG. 3 shows a Y-street configuration of distribution nodes, accordingto an embodiment.

FIG. 4 shows a Z-street configuration of distribution nodes, accordingto an embodiment.

FIG. 5 shows a sequence of bandwidth allocation scheduling actionsoccurring at a distribution node, according to an embodiment.

FIG. 6 shows a proposed bandwidth allocation schedule, an adjustedproposed bandwidth allocation schedule, and a final bandwidth allocationschedule, according to an embodiment.

FIG. 7 shows adjusted proposed bandwidth allocation schedules of asecond distribution node and a third distribution node in response to apropose bandwidth allocation of a first distribution node, and a finalbandwidth allocation schedule, according to an embodiment.

FIG. 8 shows a series of adjusted proposed bandwidth allocationschedules of a second distribution node and a third distribution node,wherein the allocations are distributed according to differentpercentages, according to an embodiment.

FIG. 9 is a flow chart that includes steps of a method of dynamicbandwidth allocation for a wireless mesh network, according to anembodiment.

DETAILED DESCRIPTION

The embodiments described include methods, apparatuses, and systems fordynamic bandwidth allocation of wireless mesh networks. At least someembodiments include distribution nodes of a wireless mesh networkdetermining bandwidth allocation scheduling of communication between thedistribution nodes using negotiated messages that are communicatedbetween the distribution nodes.

FIG. 1 shows nodes of a wireless mesh network, according to anembodiment. As shown, the wireless mesh network includes distributionnodes 110, 120, 130, 140, 150, 160 and client nodes 111, 112, 123, 124,145, 146. Distribution nodes may or may not include client nodes.Further, the distribution nodes 110, 120, 130, 140, 150, 160 operate todistribute wireless information to other distribution nodes and/or toclient nodes. The client nodes 111, 112, 123, 124, 145, 146 are endpointedge devices that generally originate or consume information. At leastsome of the described embodiments provide coordination and control ofthe transmission and reception of the information communicated betweenthe nodes of the wireless mesh network.

FIG. 2 shows distribution nodes 210, 220 and client nodes 211, 212, 223,224 of a wireless mesh network, according to an embodiment. For anembodiment, a first distribution node 210 operates to identify acommunication link with a second distribution node 220 of the wirelessmesh network. For an embodiment, identification of the communicationlink is provided to the first distribution node. For an embodiment, anupstream controller provides the identification of the communicationlink to the first distribution node. For an embodiment, firstdistribution node is further provided with the type of node(distribution node or client node) at the other end of the communicationlink. For an embodiment, the first distribution node operates toself-determine the identification of the communication link to thesecond distribution node.

For an embodiment, the first distribution node 210 further operates togenerate a proposed bandwidth allocation schedule for wirelesscommunication of information between the first distribution node and thesecond distribution node based on data traffic requirements of the firstdistribution node from its connected distribution nodes and clientnodes. For an embodiment, the proposed bandwidth allocation scheduleincludes time allocations. For an embodiment, the proposed bandwidthallocation schedule includes frequency allocations. For an embodiment,the proposed bandwidth allocation schedule includes time and frequencyallocations.

For at least some embodiments, the data traffic requirements of thefirst distribution node 210 are dependent on the demands of the nodesthat are linked to the first distribution node 210. That is, as shown,the second distribution node 220 and client nodes 211, 212 all have datatraffic demands to be satisfied by the first distribution node 210. Foran embodiment, the proposed bandwidth allocation schedule reflects thedata traffic demands of each of the linked nodes.

For at least some embodiments, the data traffic demand of each of thelinked nodes is based at least in part on bandwidth requirements of thelinked node. For an embodiment, each linked node, whether the linkednode is a distribution node or a client node, reports the bandwidthrequirements to the corresponding distribution node. For an embodiment,the bandwidth requirements includes a number of bytes pending fortransmission to the corresponding linked node, and/or an arrival rate interms of incoming bytes or packets per second, and/or a link rate (forexample, MCS (modulation and coding scheme). For an embodiment, thefirst distribution node determines the a number of bytes pending fortransmission to the corresponding linked node, and/or an arrival rate interms of incoming bytes or packets per second as the bytes or packetsare received at the first distribution node for transmission to theconnecting nodes.

For at least some embodiments, the first distribution node communicatesto the second distribution node its own bandwidth requirement (aspreviously defined) for the second distribution node, which the seconddistribution node uses for adjusting the proposed bandwidth allocationschedule. Further, the first distribution node determines the bandwidthrequirements for outgoing traffic to all of the nodes linked to thefirst distribution node.

For at least some embodiments, the second distribution node 220 receivesthe proposed bandwidth allocation schedule from the first distributionnode 210. Further, for at least some embodiments, the seconddistribution node 220 adjusts the proposed bandwidth allocation schedulebased upon data traffic requirements of the second distribution node220. As shown, the second distribution node 220 includes connections tothe first distribution node 210 and client nodes 223, 224. Accordingly,at least some embodiments of the scheduling are based on data trafficdemands of the e linked nodes 223, 224. For at least some embodiments,the data traffic demands of these linked nodes is based at least in parton queue sizes and traffic rates requested by the linked nodes.

As previously stated, the data traffic demand of each of the linkednodes is based at least in part on bandwidth requirements of the linkednode. For an embodiment, each linked node, whether the linked node is adistribution node or a client node, reports the bandwidth requirementsto the corresponding distribution node. For an embodiment, the bandwidthrequirements includes a number of bytes pending for transmission to thecorresponding linked node, and/or an arrival rate in terms of incomingbytes or packets per second, and/or the link rate (for example, MCS).For an embodiment, the second distribution node determines the number ofbytes pending for transmission to the corresponding linked node, and/oran arrival rate in terms of incoming bytes or packets per second, and/orthe link rate (for example, MCS) as the bytes or packets are received atthe second distribution node for transmission to the connecting nodes.

For at least some embodiments, the second distribution node 220communicates the adjusted proposed bandwidth allocation schedule to thefirst distribution node 210. The adjusted proposed bandwidth allocationschedule is then used for communicating information between the firstdistribution node and the second distribution node.

For at least some embodiments, each of the distribution nodes performsthe above-described operations of the first distribution node. That is,each of the distribution nodes generates a proposed bandwidth allocationschedule which is communicated to all corresponding distributionnode(s). Each distribution node then receives back an adjusted proposedbandwidth allocation schedule from all corresponding distributionnode(s) which is used as the schedule for communicating between thedistribution node and the other distribution node(s). Accordingly, eachof the distribution nodes is also receiving a proposed bandwidthallocation schedule which the distribution node adjusts and communicatesback. For an embodiment, the proposed bandwidth allocation schedulegenerated by the first distribution node is for transmit traffic (at thefirst distribution node), and the proposed bandwidth allocation scheduleadjusted by the second distribution node is for receive traffic (at thesecond distribution node).

For at least some embodiments, the proposed bandwidth allocationschedule and the adjusted proposed bandwidth allocation schedule arecommunicated between the first distribution node and the seconddistribution node through a negotiated message. For an embodiment, thenegotiated message is included within keep alive messages that arecommunicated between the distribution nodes. For an embodiment, adefault bandwidth allocation schedule is used if the negotiated messageexchange fails.

For at least some embodiments, after the proposed bandwidth allocationschedule and the adjusted proposed bandwidth allocation schedule havebeen communicated between the first distribution node 210 and the seconddistribution node 220, the first distribution node 210 then allocates atleast a portion of available bandwidth allocations of the adjustedproposed bandwidth allocation schedule to client nodes of the firstdistribution node based on data traffic requirements of the clientnodes. That is, the proposed bandwidth allocation schedule and theadjusted proposed bandwidth allocation schedule may not allocate all ofthe available bandwidth allocation. For an embodiment, at least aportion of remaining available bandwidth that has not been allocated isallocated to the client nodes linked to the first distribution node.

For an embodiment, the data traffic requirement of each client node isbased at least in part on bandwidth requirements of the client node. Foran embodiment, the bandwidth requirements include a number of bytespending for transmission to the corresponding linked distribution node,and/or an arrival rate in terms of incoming bytes or packets per second,and/or the link rate. For an embodiment, the client node determines thelink rate, and/or the number of bytes pending for transmission to thecorresponding linked distribution node, and/or an arrival rate in termsof incoming bytes or packets per second as the bytes or packets arereceived at the client node for transmission to the connecting nodes.

For at least some embodiment, the bandwidth allocations are timeallocations. For at least some embodiments, the proposed bandwidthallocation schedule includes a proposed bitmap of suggested bandwidthallocations (time allocations). The second distribution node thenadjusts the bitmap, strictly as a subset of proposed bitmap, based onthe data traffic demands of the second distribution node. That is, forat least some embodiments, the proposed bandwidth allocation includesthe proposed bitmap, and the adjusted proposed bandwidth allocationincludes the adjusted proposed bit map.

For at least some embodiments, the proposed bandwidth allocationschedule includes a percentage of an entire bit map, but does notinclude suggested bandwidth allocations of the bit map. That is, ratherthat specifying specific allocations of the available band allocationsof the schedule, a percentage of the bandwidth allocations is specified.The second distribution node then adjusts the percentage to be equal orlower based on the data traffic demands of the second distribution node.For an embodiment, the proposed bandwidth allocation schedule includes apercentage of an entire bit map when the number of distribution nodeslinked to the first distribution node is not greater than two.

For at least some embodiments, the proposed bandwidth allocationschedule distributes the bandwidth allocations across the bit map.Distributing the bandwidth allocations across the bitmap can improvelatency. That is, for example, evenly distributing the bandwidthallocations across the bitmap can provide better latency and jitterperformance of communication between the first distribution node and thesecond distribution node compared to distributing the bandwidthallocations in only one portion of the bitmap.

For at least some embodiments, the proposed bandwidth allocationschedule includes control slots, wherein communication of informationcannot be scheduled during the control slots. For an embodiment, theinformation within the control slots includes wireless network controlinformation.

For an embodiment, the locations of the control slots remain the sameduring or over an association time between peer distribution nodes, suchas, the first distribution node and the second distribution node.However, for an embodiment, the locations of the control slots withinthe bandwidth allocation schedule can change over differentassociations.

For at least some embodiments, placement of the control slots for eachlink of the distribution node of the wireless mesh network is differentthan other links of the distribution node. That is, the control slot ofeach link of the distribution node is exclusive. For an embodiment inthe Z street case, an upstream controller selects/allocates theplacements of the control slots to prevent conflicts between differentlinks of the same distribution node.

FIG. 2 further shows a first sector 214 of the first distribution node210 and a second sector 216 of the first distribution node 210. For atleast some embodiments, each sector 214, 216 includes a radio. Asdescribed, a communication link is identified with the seconddistribution node 220 of the wireless mesh network. For an embodiment,this communication link is through the first sector 214 of the firstdistribution node 210. For an embodiment, a communication (second ordifferent) link is identified with another distribution node 280 of thewireless mesh network. For an embodiment, this communication link isthrough the second sector 216 of the first distribution node 210.Further, the described embodiments for generating and exchanging theproposed bandwidth allocation schedule and adjusted proposed bandwidthallocation schedule between the first distribution node 210 and thesecond distribution node 220 can additionally be performed between thefirst distribution node 210 and the other distribution node 280. Thatis, a first proposed bandwidth allocation schedule and a first adjustedproposed bandwidth allocation schedule are generated and exchangedbetween the first sector 214 of the first distribution node 210 and thesecond distribution node 220, and a second proposed bandwidth allocationschedule and a second adjusted proposed bandwidth allocation scheduleare generated and exchanged between the second sector 216 of the firstdistribution node 210 and the other distribution node 280. Clearly, eachdistribution node can include any number of sectors, and generates andreceives the corresponding number of proposed bandwidth allocationschedules and adjusted proposed bandwidth allocation schedules. For atleast some embodiments, the scheduling of each of the sectors 214, 216is independent of the scheduling of the other sector 214, 216.

FIG. 2 also shows a central or upstream controller 290. The controller290 operates to provide at least some control information to thedistribution node 210.

FIG. 3 shows a Y-street configuration of distribution nodes, accordingto an embodiment. As shown, the first distribution node 310 is linked tothe second distribution node 320, and to a third distribution node 330.For at least some embodiments, the first distribution node 310communicates proposed bandwidth allocation schedules to both the seconddistribution node 320 and the third distribution node 330. The firstdistribution node then receives back from both the second distributionnode 320 and the third distribution node 330 adjusted proposed bandwidthallocation schedules.

Specifically, for an embodiment, the first distribution node 310operates to generate a proposed bandwidth allocation schedule for thesecond distribution node 320 based on data traffic requirements of thefirst distribution node 310, and receives back an adjusted bandwidthallocation schedule from the second distribution node 320. Further, thefirst distribution node 310 of a wireless mesh network identifies acommunication link with the third distribution node 330 of the wirelessmesh network. The first distribution node 310 further operates togenerate a proposed bandwidth allocation schedule for wirelesscommunication of information between the first distribution node 310 andthe third distribution node 330 based on data traffic requirements ofthe first distribution node 310. For an embodiment, the data trafficrequirements of the first distribution node 310 is determined based ontraffic requirements of nodes linked to the first distribution node,such as, distribution nodes 320, 330 and client nodes 311, 312. For anembodiment, the data traffic requirements of the second distributionnode 320 is determined based on traffic requirements of nodes linked tothe second distribution node 320, such as, distribution nodes 310 andclient nodes 323, 324.

For at least some embodiments, the third distribution node 330 receivesthe proposed bandwidth allocation schedule and adjusts the proposedbandwidth allocation schedule based upon data traffic requirements ofthe third distribution node 330. The first distribution node 310receives the adjusted proposed bandwidth allocation schedule from thethird distribution node 330, and communicates information with thesecond distribution node 320 and the third distribution 330 according tothe adjusted proposed bandwidth allocation schedule of the seconddistribution node 320 and the adjusted proposed bandwidth allocationschedule of the third distribution node 330. For an embodiment, the datatraffic requirements of the third distribution node 330 is determinedbased on data traffic requirements of nodes linked to the thirddistribution node 330, such as, distribution nodes 310 and client node335. It is to be understood that the second distribution node 320 andthe third distribution node 330 generate proposed bandwidth allocationschedules as well, and the first distribution node receives theseproposed bandwidth allocation schedules, adjusts the proposed bandwidthallocation schedules (based on the data traffic requirements of thefirst distribution node 310), and communicates the adjusted schedulesback to the second distribution node 320 and the third distribution node330.

FIG. 4 shows a Z-street configuration of distribution nodes, accordingto an embodiment. As shown, the first distribution node 410 is linked tothe second distribution node 420 and the third distribution node 430.Further, the second distribution node 420 is linked to the firstdistribution node 410 and a fourth distribution node 440. Thisconfiguration includes the formation of a Z by the links between thefourth distribution node 440, the second distribution node 420, thefirst distribution node 410, and the third distribution node 430.Further, the first distribution node includes client nodes 411, 412, thesecond distribution node includes client nodes 423, 424, the thirddistribution node 430 includes client node 435, and the fourthdistribution node 440 includes client node 446.

Accordingly, at least some embodiments include identifying that thefirst distribution node and the second distribution node have a linkbetween each other, the first distribution node has another link withina third distribution node, and the second distribution node has anotherlink with a fourth distribution node. That is, a Z-street configurationis identified.

For at least some embodiments, once the Z-street configuration has beenidentified, the first distribution node 410 and the second distributionnode 420 are provided with priority zones. For at least some embodiment,a priority zone provided to the first distribution node 410 identifiesportions of the proposed bandwidth allocation schedule that can beallocated to each of the distribution nodes the first distribution node410 is linked to. Further, a priority zone provided to the seconddistribution node 420 identifies portions of the proposed bandwidthallocation schedule that can be allocated to each of the distributionnodes the second distribution node 410 is linked to. The priority zonesare provided to prevent conflicts in the scheduling.

For at least some embodiments, the first distribution node 410 generatesthe proposed bandwidth allocation schedule according to its providedpriority zone. For at least some embodiments, the second distribution420 node generates the adjusted time slot schedule according to itsprovided priority zone.

For a specific Z-street configuration, the first distribution node 410is only linked to the second distribution node 420 and the thirddistribution node 430, and the second distribution node 420 is onlylinked to the first distribution node 410 and the fourth distributionnode 440, and wherein the first distribution node 410 and the seconddistribution nodes 420 are provided with binary priority zones. That is,as previously described, the distribution nodes can be linked to anynumber of other distribution nodes. However, for this specificconfiguration, the first distribution node is only linked to two otherdistribution nodes, and the second distribution nodes is only linked totwo other distribution nodes. For this specific configuration, thepriority zones are binary.

That is, a first priority zone of the first distribution node allocatesbandwidth allocations within the first priority zone that is a binary ofa second priority zone of the second distribution node that allocatesbandwidth allocations within the second priority zone. The firstpriority zone and the second priority zone are selected to preventconflicts between the communication of the first distribution node andthe second distribution node. That is, for an embodiment, the firstpriority zone and the second priority zone are mutually exclusive, anddo not overlap.

For an embodiment, an upstream controller (such as previously describedupstream or central controller 290) operates to identify that the firstdistribution node and the second distribution node have the link betweeneach other, the first distribution node has the other link with thethird distribution node, and the second distribution node has the otherlink with the fourth distribution node. Further, for an embodiment, theupstream controller provides all the distribution nodes with priorityzones.

FIG. 5 shows a sequence of bandwidth allocation scheduling actionsoccurring at a distribution node (for example, at the first distributionnode), according to an embodiment. Each block of the sequence designatesactions of the distribution node. A first action 510 of the distributionnode includes generating and communicating the proposed bandwidthallocation schedule to one or more peer distribution nodes (such as, thesecond distribution node). A second action 520 includes the distributionnode responding to a proposed bandwidth allocation schedule receivedfrom a peer node with an adjusted proposed bandwidth allocationschedule. A third action 530 generating and communicating a bandwidthallocation schedule with one or more client nodes linked to thedistribution node.

The sequence of actions of the distribution node of FIG. 5 illuminatesthat each of the distribution nodes of the wireless mesh network areperforming the described operations of generating proposed bandwidthallocation schedules and adjusting received proposed bandwidthallocation schedules.

FIG. 6 shows a proposed bandwidth allocation schedule, an adjustedproposed bandwidth allocation schedule, and a final bandwidth allocationschedule, according to an embodiment. The bandwidth allocation schedulessuggest time slots, but as previously described, the bandwidthallocations can be time and/or frequency allocations. The proposedbandwidth allocation schedule 610 is generated by the first distributionnode and communicated to the second distribution node, wherein theproposed bandwidth allocation schedule 610 is generated based on datatraffic requirements of the first distribution node. As previouslydescribed, the second distribution node receives the proposed bandwidthallocation schedule 610, and the second distribution node generates anadjusted proposed bandwidth allocation schedule 612 based on theproposed bandwidth allocation schedule 610 and based upon data trafficrequirements of the second distribution node. Further, for at least someembodiments, the first distribution node receives the proposed bandwidthallocation schedule 612 and generates a final bandwidth allocationschedule 614 by allocating at least a portion of available bandwidthallocations of the adjusted proposed bandwidth allocation schedule toclient nodes of the first distribution node based on data trafficrequirements of the client nodes. The first distribution node thencommunicates information with the second distribution node and theclient nodes according to the final bandwidth allocation schedule.

FIG. 7 shows adjusted proposed bandwidth allocation schedules of asecond distribution node and a third distribution node in response to apropose bandwidth allocation of a first distribution node, and a finalbandwidth allocation schedule, according to an embodiment. For theadjusted proposed bandwidth allocation schedules of FIG. 7, each of thesecond distribution node and the third distribution node receives aproposed bandwidth allocation schedules includes a ratio or percentagerather than specific allocations. The second and third distributionnodes then generate the adjusted proposed bandwidth allocation schedules710, 720 based on the provided ratio or percentage, and based upon theirdata traffic requirements. As shown in FIG. 7, the second distributionnode was provided with a ratio or percentage of 10/16, 5/8, or 62.5%,and the third distribution node was provided with a ratio or percentageof 6/16, 3/8, or 37.5%.

For at least some embodiments, after receiving the adjusted proposedbandwidth allocation schedules of a second distribution node and a thirddistribution node, the first distribution node generates a finalbandwidth allocation schedule 730.

FIG. 8 shows a series of adjusted proposed bandwidth allocationschedules of a second distribution node and a third distribution node,wherein the allocations are distributed according to differentpercentages, according to an embodiment. As previously described,distributing the allocations rather than concentrating the allocationscan result in better latency and jitter performance of wirelesscommunication through the distribution nodes.

The adjusted proposed bandwidth allocation schedules 801, 802, 803, 804,805, 806 are generated by the second distribution node in response toproposed bandwidth allocation schedules having increasingly greaterpercentages or ratios. As shown, the allocations are distributedsomewhat evenly across available slots.

The adjusted proposed bandwidth allocation schedules 811, 812, 813, 814,815, 816 are generated by the third distribution node in response toproposed bandwidth allocation schedules having increasingly greaterpercentages or ratios. As shown, the allocations are distributedsomewhat evenly across available slots.

For at least some embodiments, the first distribution node receives theadjusted proposed bandwidth allocation schedule (that is, one of thebandwidth allocation schedules 801, 802, 803, 804, 805, 806) generatedby the second distribution node, and the first distribution nodereceives the adjusted proposed bandwidth allocation schedule (that is,one of the bandwidth allocation schedules 811, 812, 813, 814, 815, 816)generated by the third distribution node. The first distribution nodeintegrates the bandwidth allocation generated by the second distributionnode and the bandwidth allocation generated by third distribution node.Note that the combination of the bandwidth allocation generated by thesecond distribution node and the bandwidth allocation generated by thirddistribution node can only add up to at most 100% of the bit map, notmore. That is, more slots than are allowable by the bit map cannot beallocated to the second distribution node and the third distributionnode.

FIG. 9 is a flow chart that includes steps of a method of dynamicbandwidth allocation for a wireless mesh network, according to anembodiment. A first step 910 includes identifying, by a firstdistribution node of a wireless mesh network, a communication link witha second distribution node of the wireless mesh network. A second step920 includes generating, by the first distribution node, a proposedbandwidth allocation schedule for wireless communication of informationbetween the first distribution node and the second distribution nodebased on data traffic requirements of the first distribution node. Athird step 930 includes the second distribution node receiving theproposed bandwidth allocation schedule, wherein the second distributionnode adjusts the proposed bandwidth allocation schedule based upon datatraffic requirements of the second distribution node. A fourth step 940includes receiving, by the first distribution node, the adjustedproposed bandwidth allocation schedule from the second distributionnode. A fifth step 950 includes communicating, by the first distributionnode, information with the second distribution node according to theadjusted proposed bandwidth allocation schedule.

For an embodiment, the proposed bandwidth allocation schedule and theadjusted proposed bandwidth allocation schedule are communicated betweenthe first distribution node and the second distribution node through anegotiated message. For an embodiment, the negotiated message isincluded within keep alive messages, which are communicated between thedistribution nodes.

As previously described, at least some embodiments further includeallocating, by the first distribution node, at least a portion ofavailable bandwidth allocations of the adjusted proposed bandwidthallocation schedule to client nodes of the first distribution node basedon data traffic requirements of the client nodes.

For at least some embodiments, the data traffic demand of each of thelinked nodes (distribution nodes and/or client nodes) is based at leastin part on bandwidth requirements of the linked node. For an embodiment,each linked node, whether the linked node is a distribution node or aclient node, reports the bandwidth requirements to the correspondingdistribution node. For an embodiment, the bandwidth requirementsincludes a number of bytes pending for transmission to the correspondinglinked node, an arrival rate in terms of incoming bytes or packets persecond, and/or a link rate (MCS). For an embodiment, the firstdistribution node determines the a number of bytes pending fortransmission to the corresponding linked node, and/or an arrival rate interms of incoming bytes or packets per second as the bytes or packetsare received at the first distribution node for transmission to theconnecting nodes.

As previously described, at least some embodiments further includeidentifying, by the first distribution node of the wireless meshnetwork, a communication link with a third distribution node of thewireless mesh network. The communication links between the firstdistribution node and the second distribution node, and between thefirst distribution node and the third distribution node for a Y-streetconfiguration. At least some embodiments further include generating, bythe first distribution node, a proposed bandwidth allocation schedulefor wireless communication of information between the first distributionnode and the third distribution node based on data traffic requirementsof the first distribution node, wherein the third distribution nodereceives the proposed bandwidth allocation schedule, and wherein thethird distribution node adjusts the proposed bandwidth allocationschedule based upon data traffic requirements of the third distributionnode, receiving, by the first distribution node, the adjusted proposedbandwidth allocation schedule from the third distribution node, andcommunicating, by the first distribution node, information with thesecond distribution node and the third distribution according to theadjusted proposed bandwidth allocation schedule of the seconddistribution node and the adjusted proposed bandwidth allocationschedule of the third distribution node.

As previously described, for at least some embodiments, the proposedbandwidth allocation schedule includes a percentage of an entire bitmap, but does not include suggested bandwidth allocations of the entirebit map.

As previously described, for at least some embodiments, the proposedbandwidth allocation schedule distributes the bandwidth allocationsacross the proposed bandwidth allocation schedule (bit map). Aspreviously described, and shown in FIG. 8, distributing the bandwidthallocations across the schedule can improve latency. That is, forexample, evenly distributing the bandwidth allocations across theschedule can provide better latency and jitter performance ofcommunication between the first distribution node and the seconddistribution node compared to distributing the bandwidth allocations inonly one portion of the schedule.

As previously described, for at least some embodiments, the proposedbandwidth allocation schedule includes control slots, whereincommunication of information cannot be scheduled during the controlslots. The locations of the control slots within the proposed bandwidthallocation schedule can change over time. However, the locations of thecontrol slots remain the same during or over an association time withpeer distribution nodes.

As previously described, for at least some embodiments, placement of thecontrol slots for each link of the first distribution node to otherdistribution nodes and client nodes of the wireless mesh network isdifferent than other links of the first distribution node to the otherdistribution nodes and the client nodes. That is, the control slot ofeach link of the distribution node is exclusive and does not overlapwith placement of the control slot of other link of the distributionnode.

For an embodiment, an upstream controller selects/allocates theplacements of the control slots to prevent conflicts between differentlinks of the same distribution node.

An embodiment includes identifying a Z-street distribution nodeconfiguration. Specifically, an embodiment includes identifying that thefirst distribution node and the second distribution node have a linkbetween each other, the first distribution node has another link withina third distribution node, and the second distribution node has anotherlink with a fourth distribution node. Further, at least some embodimentsinclude providing the first distribution node and the seconddistribution node with priority zones, wherein the first distributionnode generates the proposed bandwidth allocation schedule according toits provided priority zone, and the second distribution node generatesthe adjusted bandwidth allocation schedule according to its providedpriority zone.

For a specific Z-street configuration, the first distribution node isonly linked to the second distribution node and the third distributionnode, and the second distribution node is only linked to the firstdistribution node and the fourth distribution node, and wherein thefirst distribution node and the second distribution nodes are providedwith binary priority zones. For an embodiment, a first priority zone ofthe first distribution node allocates bandwidth allocations within thefirst priority zone that is a binary of a second priority zone of thesecond distribution node that allocates bandwidth allocations within thesecond priority zone. That is, the control slot of each link of thedistribution node is exclusive. The first priority zone and the secondpriority zone are selected to prevent conflicts between thecommunication of the first distribution node and the second distributionnode.

For an embodiment, an upstream controller operates to identify that thefirst distribution node and the second distribution node have the linkbetween each other, the first distribution node has the other linkwithin the third distribution node, and the second distribution node hasthe other link with the fourth distribution node, and the upstreamcontroller provides the first distribution node and the seconddistribution node with priority zones.

Although specific embodiments have been described and illustrated, theembodiments are not to be limited to the specific forms or arrangementsof parts so described and illustrated. The described embodiments are toonly be limited by the claims.

What is claimed:
 1. A method, comprising: identifying, by a firstdistribution node of a wireless mesh network, a communication link witha second distribution node of the wireless mesh network; generating, bythe first distribution node, a proposed bandwidth allocation schedulefor wireless communication of information between the first distributionnode and the second distribution node based on data traffic requirementsof the first distribution node; wherein the second distribution nodereceives the proposed bandwidth allocation schedule, and wherein thesecond distribution node adjusts the proposed bandwidth allocationschedule based upon data traffic requirements of the second distributionnode; receiving, by the first distribution node, the adjusted proposedbandwidth allocation schedule from the second distribution node; andcommunicating, by the first distribution node, information with thesecond distribution node according to the adjusted proposed bandwidthallocation schedule.
 2. The method of claim 1, further comprising:allocating, by the first distribution node, at least a portion ofavailable bandwidth allocations of the adjusted proposed bandwidthallocation schedule to client nodes of the first distribution node basedon data traffic requirements of the client nodes.
 3. The method of claim1, further comprising: identifying, by the first distribution node ofthe wireless mesh network, a communication link with a thirddistribution node of the wireless mesh network; generating, by the firstdistribution node, a proposed bandwidth allocation schedule for wirelesscommunication of information between the first distribution node and thethird distribution node based on data traffic requirements of the firstdistribution node; wherein the third distribution node receives theproposed bandwidth allocation schedule, and wherein the thirddistribution node adjusts the proposed bandwidth allocation schedulebased upon data traffic requirements of the third distribution node;receiving, by the first distribution node, the adjusted proposedbandwidth allocation schedule from the third distribution node; andcommunicating, by the first distribution node, information with thesecond distribution node and the third distribution according to theadjusted proposed bandwidth allocation schedule of the seconddistribution node and the adjusted proposed bandwidth allocationschedule of the third distribution node.
 4. The method of claim 1,wherein the proposed bandwidth allocation schedule includes a percentageof a bit map, but does not include suggested bandwidth allocations ofthe bit map.
 5. The method of claim 1, wherein the proposed bandwidthallocation schedule distributes bandwidth allocations across theproposed bandwidth allocation schedule.
 6. The method of claim 1,wherein the proposed bandwidth allocation schedule includes controlslots, wherein communication of information cannot be scheduled duringthe control slots.
 7. The method of claim 6, wherein placement of thecontrol slots for each link of the first distribution node to otherdistribution nodes and client nodes of the wireless mesh network isdifferent than other links of the first distribution node to the otherdistribution nodes and the client nodes.
 8. The method of claim 1,further comprising: identifying that the first distribution node and thesecond distribution node have a link between each other, the firstdistribution node has another link within a third distribution node, andthe second distribution node has another link with a fourth distributionnode.
 9. The method of claim 8, further comprising: providing the firstdistribution node and the second distribution node with priority zones,wherein the first distribution node generates the proposed bandwidthallocation schedule according to its provided priority zone; and thesecond distribution node generates the adjusted bandwidth allocationschedule according to its provided priority zone.
 10. The method ofclaim 9, wherein the first distribution node is only linked to thesecond distribution node and the third distribution node, and the seconddistribution node is only linked to the first distribution node and thefourth distribution node, and wherein the first distribution node andthe second distribution nodes are provided with binary priority zones.11. The method of claim 9, wherein an upstream controller identifiesthat the first distribution node and the second distribution node havethe link between each other, the first distribution node has the otherlink within the third distribution node, and the second distributionnode has the other link with the fourth distribution node; and providesthe first distribution node and the second distribution node withpriority zones.
 12. A wireless network, comprising: a first distributionnode; a second distribution node; wherein the first distribution nodeoperates to: identify a communication link with the second distributionnode; generate a proposed bandwidth allocation schedule for wirelesscommunication of information between the first distribution node and thesecond distribution node based on data traffic requirements of the firstdistribution node; wherein the second distribution node operates to:receive the proposed bandwidth allocation schedule; and adjust theproposed bandwidth allocation schedule based upon data trafficrequirements of the second distribution node; wherein the firstdistribution node further operates to: receive the adjusted proposedbandwidth allocation schedule from the second distribution node; andcommunicate information with the second distribution node according tothe adjusted proposed bandwidth allocation schedule.
 13. The wirelessnetwork of claim 12, wherein the first distribution node operates to:allocate at least a portion of available bandwidth allocations of theadjusted proposed bandwidth allocation schedule to client nodes of thefirst distribution node based on data traffic requirements of the clientnodes.
 14. The wireless network of claim 12, wherein the firstdistribution node operates to: identify a communication link with athird distribution node of the wireless mesh network; generate aproposed bandwidth allocation schedule for wireless communication ofinformation between the first distribution node and the thirddistribution node based on data traffic requirements of the firstdistribution node; wherein the third distribution node receives theproposed bandwidth allocation schedule, and wherein the thirddistribution node adjusts the proposed bandwidth allocation schedulebased upon data traffic requirements of the third distribution node;receive the adjusted proposed bandwidth allocation schedule from thethird distribution node; and communicate information with the seconddistribution node and the third distribution according to the adjustedproposed bandwidth allocation schedule of the second distribution nodeand the adjusted proposed bandwidth allocation schedule of the thirddistribution node.
 15. The wireless network of claim 12, wherein thefirst distribution node and the second distribution node are identifiedto have a link between each other, the first distribution node isidentified to have another link within a third distribution node, andthe second distribution node is identified to have another link with afourth distribution node.
 16. The wireless network of claim 15, whereinthe first distribution node and the second distribution node areprovided with priority zones, wherein the first distribution nodegenerates the proposed bandwidth allocation schedule according to itsprovided priority zone; and the second distribution node generates theadjusted time slot schedule according to its provided priority zone. 17.The wireless network of claim 16, wherein the first distribution node isonly linked to the second distribution node and the third distributionnode, and the second distribution node is only linked to the firstdistribution node and the fourth distribution node, and wherein thefirst distribution node and the second distribution nodes are providedwith binary priority zones.
 18. The wireless network of claim 15,further comprising an upstream controller, wherein the upstreamcontroller operates to: identify that the first distribution node andthe second distribution node have the link between each other, the firstdistribution node has the other link within the third distribution node,and the second distribution node has the other link with the fourthdistribution node; and provide the first distribution node and thesecond distribution node with priority zones.
 19. The wireless networkof claim 12, wherein the proposed bandwidth allocation schedule includescontrol slots, wherein communication of information cannot be scheduledduring the control slots, wherein placement of the control slots foreach distribution node of the wireless mesh network is different that atleast one other distribution node.
 20. A first distribution nodeoperative to: identify a communication link with a second distributionnode of a wireless mesh network; generate a proposed bandwidthallocation schedule for wireless communication of information betweenthe first distribution node and the second distribution node based ondata traffic requirements of the first distribution node; wherein thesecond distribution node receives the proposed bandwidth allocationschedule, and wherein the second distribution node adjusts the proposedbandwidth allocation schedule based upon data traffic requirements ofthe second distribution node; wherein the first distribution nodefurther operates to: receive the adjusted proposed bandwidth allocationschedule from the second distribution node; and communicate informationwith the second distribution node according to the adjusted proposedbandwidth allocation schedule.